CrystalMaker Guide: Cambridge FDAT Files
Example FDAT fileAn example FDAT file is listed below:-
File ImportCrystalMaker extracts virtually all information contained in an FDAT file. Many of the header flags (e.g., errors, refinement, data collection) are interpreted, and diagnostic messages printed in the Notebook Window. Errors in unit cell parameters are also extracted, and used for bond-distance error propagation. SymmetryAlthough the spacegroup symbol and number is given, CrystalMaker prefers to use the symmetry operators instead-this avoids problems with non-standard settings! (A technical note: CrystalMaker does a lot of behind-the-scenes work converting the CSD symmetry operators to conventional G.E.P.'s: if there's a centre of symmetry at the origin we add the extra operators, and we also use the lattice type to "prune" the (redundant) symmetry operators corresponding to lattice translations. Thus, if one examines the imported G.E.P's using the Symmetry Options dialog, they should correspond to equivalent positions listed in the International Tables for Crystallography). AtomsCrystalMaker only imports atoms in the asymmetric unit; symmetry-generated atoms, if listed in the file, are ignored. The atom colours correspond to CrystalMaker's default atom colours: these can be edited or imported from a text file using the Elements dialog (Edit > Elements). If you import a large number of organic structures, we recommend importing the CSD Default Radii element table, and then saving these data in your preferences file. Automatic Bond GenerationCrystalMaker uses a very concise way of representing bonding information-the bond specification cards. The individual bonds listed at the end of the FDAT file are therefore largely irrelevant. However, we search the bonds list to deduce the intended bonding pattern, and use this as a basis for CrystalMaker's own bond search. Thus, if the FDAT bond list contains CC, CH and CO bonds, we create three separate bond specifications for these bonds. To determine the maximum bond lengths for each bond specification, we use the bond length tolerance in the CSD file (usually 0.40 Å) plus the sum of the atomic radii involved. Usually these radii are listed in the FDAT file. If the radii can't be found in the FDAT file, CrystalMaker searches its own default radii-these are the radii that appear in the Elements dialog. If a radius value still can't be found, a default value of 1.0 Åis used. Because of the way CrystalMaker defines bonds, you may find that not all "requested" bonds can be found, and an alertbox will be displayed after the crystal has been imported. For example, if a molecule contains H-C and H-O bonds so that some H's are bonded to carbon but not oxygen, and vice versa, error messages will be printed in the output window. (Obviously, the carbon H will not have any bonds to O, and the oxygen H won't have any bonds to carbon). In these cases, you can disregard the messages. If you still don't get the bonds you want, you can easily change the bonding specifications using the Edit Bond Specifications dialog. © 1998 CrystalMaker Software. All rights reserved |